Hi Dragan,

>And the precision of the seconds() function has gone from 1ms to 10ms somewhere between NT4 and W2K or so.

On NT you can change the resolution for SECONDS() using the timeBeginPeriod API function:

Declare long timeBeginPeriod in WinMM.dll long
timeBeginPeriod(1)

http://www.foxpert.com/KnowlBits_200705_5.htm

>Still, if coverage logging can have microseconds, this was surely feasible, probably by use of different API functions.

That's a Performance Counter object. You can use the QueryPerformanceCounter API functions. One problem with that is its performance, though. Although it returns timing values with the highest possible precision, the API call takes longer than other call for querying elapsed time.