Hi,
Yes, I hope that AQTime is an option that should work.
-- Profiling results from separate profiling sessions can be merged (https://support.smartbear.com/aqtime/docs/profiling-with/results/merge-results.html);
-- Why not to use TestedApps? If, for some reason, you really don't want to use them, you may consider to start AQTime from TestComplete test code via command line (https://support.smartbear.com/aqtime/docs/working-with/automating/command-line-and-exit-codes/command-line.html), wait in TestComplete until the tested application is started and drive it;
-- Just wondering, isn't it too expensive to wait for the .Net application to start and close for every test? If the tested application is stable enough it might be more performant not to close it after each and every test.
(Yes, I know the concept of 'clean known state', but I think that this is more relevant for the integration type of testing, while for the end-to end tests type (this is where TestComplete stands out) repeated restarts might be not the best idea because real end-users do not restart applications frequently.)
