I added a bit to my last post with regard side effects.
Nobody has spotted the fact that my TimerRes 'gizmo' and 'TimerInterval (Win10)' have a resolution of 0.5ms when timeBeginPeriod cannot go below 1ms. The reason is that I don't use timeBeginPeriod but a function lower down in the system - the one that timeBeginPeriod uses. Anyway, I won't go into details - it is mentioned in the first link of my last post. I read that some years go but see that it was updated in February 2017. Thanks for reminding of that paper. I have tested my system and I can get 0.5ms but I doubt that I will ever use it; although Microsoft Edge seems to.
Often worthwhile doing as we sometimes learn something that our OS vendor has not got around to telling us. <smile>my experiments showed me that
Added: Just had a thought. When my gizmos are minimised it may be worthwhile to have a message box pop up along the lines "Sorry to bother you, but you have been using a 1ms resolution for the last three hours and were probably wondering why the system had become sluggish". There again, maybe not. <Ha,Ha>