Dragan,
>Still, if coverage logging can have microseconds, this was surely feasible, probably by use of different API functions.
Yes, I think that that would be the QueryPerformanceFrequency and QueryPerformanceCounter API functions
http://msdn2.microsoft.com/en-us/library/ms644900.aspx#high_resolutionIn my computer that would be 3,391,550,000.0000 ticks per second!
[Update] I must've screwed up somewhere, that number seems awful big to be true [/Update]
[Update 2] Oh, it might be right after all, I found this
http://msdn2.microsoft.com/en-us/library/system.diagnostics.stopwatch.frequency.aspx where the guy gets 2,400,110,000 ticks per second [/Update]
"The five senses obstruct or deform the apprehension of reality."
Jorge L. Borges?
"Premature optimization is the root of all evil in programming."
Donald Knuth, repeating C. A. R. Hoare
"To die for a religion is easier than to live it absolutely"
Jorge L. Borges