ASP: Server.Execute vs. server-side includes

I suddenly realized on advantage Server.Execute() command has over server-side includes in a classic ASP: Server.Execute() is a part of normal execution flow and thus works as a conditional include. There is no normal way to include files conditionally with <!--#include file [or virtual]="_our_file.asp"-->, because those includes are treated with something like ASP preprocessor. On the other hand, local variables declared in calling file are available inside include and are not available in executed file - that's one reason I never used it.