Please note that while this is as accurate as you can get, there is a chance that it won't execute exactly on the millisecond, so that you might get (for example) 950 calls per second versus 1000.
Infact you cant get more than 64 calls per second, this is the cycle rate that timers are checked for if they have reached/passed there execution due time
//set %a 1 | set %b 0 | timerA -m 0 1 inc %a | timerB 0 1 echo -at Event count $!calc(%a - % $+ b) total events now % $+ a $(|,) set %b % $+ a
[12:04:26.485] Event count 106 total events now 106
[12:04:27.485] Event count 64 total events now 170
[12:04:28.485] Event count 64 total events now 234
[12:04:29.485] Event count 64 total events now 298
[12:04:30.485] Event count 64 total events now 362
[12:04:31.485] Event count 64 total events now 426
[12:04:32.485] Event count 64 total events now 490
[12:04:33.485] Event count 64 total events now 554
[12:04:34.485] Event count 64 total events now 618
Ignore the first one, thats due to syncing problems with when the once per second timer goes off, following that as you can see the result is 64 events per second.
* this is NT, win9x might have a different rate im not sure.
