title: SetTimer() pitfalls
body: <p>I have a windowless timer (no WM_TIMER) which fires a callback function only once when a given time period is elapsed. It is implemented as a <code>SetTimer()/KillTimer()</code>. Time periods are small enough: 100-300 milliseconds. </p>
  
  <p>Is that cheap enough (I mean performance) to call <code>SetTimer()/KillTimer()</code> pair for every such short time interval?</p>
  
  <p>What if I have 100 such timers which periodically call <code>SetTimer()/KillTimer()</code>? How much Window timer objects may exist simultaneously in the system?</p>
  
  <p>That is the question:
  Use a bunch of such timer objects and rely on good Windows implementation of timers, or create one Windows timer object that ticks every, say, 30 milliseconds, and subscribe all custom 100-300 milliseconds one-time timers to it.</p>
  
  <p>Thanks</p>