Consider your request received; we'll investigate better solutions for a future release.
Well, OK, at least they're thinking about it.
Maybe setitimer() would be another possibility, rather than usleep()? (and actually, re-reading the usleep() manpage, I see that whoever wrote it is saying to use nanosleep() instead. I wonder if there are the same scheduling issues with that...)
Good luck in any case...