No need to signal all here
Move these constructors higher like you would expect them to be
This resolves #34.  The solution is to track how far behind high priority tasks are, and to artifically slow down low priority tasks as high priority tasks get backed up.  This incurrs almost no overhead for high priority tasks, and the overhead for low priority tasks also remains very minimal.
Removed comment that does not help anything
Prevent a possible overflow
Just simpler to make these zero, should not be functionally any different
In very slow systems we may not wake up fast enough to notice the 100ms gap, so just increasing this to prevent an exception which may not be true
Some small unit test additions
Removed unused class from unit test