omg look at this, i was just trying it out on w2kserver, and i happened to click the FILE menu when it was running heres the results
[21:25:08.797] Event count 64 total events now 372
[21:25:09.797] Event count 64 total events now 436 clicked FILE menu sometime after this displayed
[21:25:10.422] Event count 39 total events now 475
[21:25:11.797] Event count 30 total events now 505
[21:25:12.797] Event count 30 total events now 535
[21:25:13.797] Event count 30 total events now 565
[21:25:14.797] Event count 30 total events now 595
[21:25:15.797] Event count 30 total events now 625
[21:25:16.266] Event count 30 total events now 655
[21:25:17.329] Event count 34 total events now 689 unclicked FILE menu sometime after this displayed
[21:25:18.797] Event count 38 total events now 727
[21:25:19.797] Event count 64 total events now 791
[21:25:20.797] Event count 64 total events now 855
[21:25:21.797] Event count 64 total events now 919
Assumption is that something starts eating alot of proccessor cycles just to have the drop menus up.
Ignoring what i showed above 2000 server seemed to come back with 64 a second normally, havent tried it on anything newer (than xp), from memory i think this might be to do with time slicing/cycling between applications running, I havent got the utility here to adjust the process threads priority, but i would assume if it was increased it likely would get more cycles
