Timer queue, usable without CtrlCore.
The Interface is the same as used from the Ctrl::TimerCallback in CtrlCore
To use it one does *not* need CtrlCore anymore, simply Core and Timer, where the application has a Timer instance.
Should keep in mind, that it's a timer *queue* other things wont get to execution, until a current task is finished, and the timer queue can check whether time has come for the next task.
Thus, the timing is not as accurate as maybe desired and can have "timer glitches/jitter", depending on work load..
Favorite use is to schedule some *non*-timing-critical work for "somewhere-around-in-the-future", like i.e. observe some not too strict timing constraints in custom communication protocols (answer needs to come in within X time, keep alive messages..)
For timing critical stuff, consider using OS native timer means, for WIN32 SetTimer (in windowing environment, using WM_TIMER callback) or CreateWaitableTimer for windowing-independent stuff, or even QueryPerformanceCounter. for Linux/Unix/Posix settimer function, but for Linux there is a lot anyway.