Looking at removing the testable scheduler.  It complicates the implementation, and adds a lot of code.  Furthermore I don't know of anyone currently using it, and although I think the implementation is solid, I worry about furture reqressions with other areas of code (see issue #51).

So I am just experimenting at what the implementations would look like if this was removed.
Removal of the VirtualLock infastructure since there is no longer any testable locks.  We are now just returning Objects in their place to be synchronized on.
A couple javadoc fixes for the recent changes.
Updated readme and descriptions based off the recent removal of code.
Constructor cleanup now that the StripedLock is more of an internal thing, and the user has no reason to pass it in during construction.
Merge pull request #53 from threadly/TestableScheduler_removal

TestableScheduler/VirtualLock/Virtual(Runnable/Callable) removal
This resolves #51.  This dramatically simplifies the PrioritySchedulerLimiter and reduces the code involved by constructing the returned future at submission time, and avoiding the whole "FutureListernableFuture" thing.
Removing these "FutureFuture" implementations.  They are complicated, and hard to use correctly.

In addition now that threadly no longer needs them, I think it would be advisable for others that need them to look towards other solutions.
Slight change to the description of the project.
Added the ability to get the current running count, even if not using the StatisticTracker pool.
This is no longer necessary with the removal of the TestablePriorityScheduler
Cleanup of some more javadocs, and making sure that defaults are defined within the javadocs.
Fix for checkstyle warning
Fix for a spontanious unit test failure due to a runtime being added after the task has already been removed from the runningTasks structure
Update README.md

Added litecoin address for donations
Unit test cleanup and reductions in code duplication.  I found a couple spots where we could improve coverage, simplify the test implementation, and provide similar improvements.

This change goes with a new feature "AsyncVerifier" which assists in verifying unit test actions and status for seperate threads.
Minor change to make sure we get good code coverage for the null case of priority in unit tests.
More unit test coverage, no real functional changes just trying to improve how much verification we are doing in unit tests around our collections.
Additional unit test coverage and verification improvements for the ConcurrentArrayList and the DynamicDelayQueue
We can now adjust test complexity in a single place.  This allows us to make our unit tests a bit quicker, but still allow them to easily be changed for more stressful testing.