I don't know about the Windows scheduler, but I've had Unix applications doing similar loops using usleep()'s of 100 ms. You can run 200 of those without any significant processor utilisation.