Starting on asynchronous test with the synchronous tests.

The tests may look strange at first glance since not matchers may pass where one might expect that they would fail. With finish(), willNot.finish() will pass on the first test tick even if it finishes later, the asynchronous matcher will bail out first.
MatchValues tests
willContinueTo Expectation stubbed

This matcher will address the problems with willNot.finish() and others under asynchronousTests, by waiting for truth condition when the test expires. Currently implemented with a trampoline and swizzling. When this is finished it can be modified for the Expecta project, if it is relevant to them.
Test the original implementation works
applyMatcher:to: for willContinueTo

Crashing on trampoline invoking original implementation
Original method implementation function signature is now typed
Negation for willContinueTo.

The usage of double negatives in the Unit Tests wouldn't make sense in production code, but it keeps the tests in a common format, and the failure messages the same.
Reverted zombies in scheme
Synchronous fail tests
Update README for willContinueTp
Additional Asynchronous Tests

Again, worth highlighting the lack of asymmetry between will and willNot matchers where the willNot matcher passes immediately but would fail later
sendEvent async tests.

Delay in the async signal was not respecting ordering between values being sent and errors has been modified to delay errors also.
Async tests for sendValues
Async tests for sendValuesWithCount
Merge branch 'async-tests'

Async tests now in master, will monitor unit test time, will interoperate with willContinueTo
Merge branch 'master' into willcontinue-expect