Unfortunately, that's about the best accuracy you're going to get. Stopwatches and such are not really performance tests and what you're working with is subject to processor threads and time slicing on the machine in question. TestComplete needs to identify the object, do the comparison, and report the results, all of which take processor time that are not necessarily related to the actual performance of your application. The best you can do is run several test cycles and average the values.
For better performance evaluation and profiling, you might want to consider using a tool like AQTime.
I already suspected that. Thanks for the answer anyway. I might have a look at AQTime at some day but at the moment there is not enough time for it...
Regards, David
