Allowing programmer to specify what type of deadlock avoidance
algorithm (boosted or wound-wait) to use.
Added start for code to ensure that wound-wait should provide limited ordering guarantees between endpoints.  Events should interleave.  Currently, do not.  Must investigate why not.
Switched order of write lock acquisition on local and remote
endpoint.  The change ensures that each endpoint will send a message
to the other before being rolled back.  The exchange of this message
ensures that Lamport clocks can be updated between events, and thus
that we can reuse the test for WoundWait.
Increased the time it takes before dump second thread's work into
system. This is to ensure that other side receives all Lamport clock
updates before beginning.
Re-wrote test validation: instead of printing all numbers to output, programmatically check to ensure all of one's side executes before the other's.