CB>   So it will be effected by multi-tasker delays. Also,
CB>   under a multi-tasker like Linux, you will want to go into
CB>   a sleep state. The POSIX function sleep() does this.
CB>   You could use time(), but this would be inaccurate.
   True. And Windows would prefer sleep() also, to free up
   the remainder of the time slice. I don't see a good way
   to get around this, unless you use the BIOS timer data.
   There is no guarantee that time() will even support the
   level of incrementation you desire, much less be accurate.
   I hadn't realized that clock() only incremented according
   to the processor time used by the executable.
   Guess I should read the documentation a bit closer. 

> ] I am Solo of Borg, and I've got a bad feeling about this....

---