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
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
Updated Cocoapods integration
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
Subscription counting is an explicit swizzle

Also, multiple counts due to calling [super subscribe:] are avoided by storing a pointer to the current subscriber. This is yucky and I would prefer to use a unsafe_unretained pointer, but this is unsupported by associated objects.
Merge branch 'async-tests'

Async tests now in master, will monitor unit test time, will interoperate with willContinueTo
Merge branch 'master' into be-subscribed-to
Update README for subscription counts
Pointers are stored and cleared for subscribers to avoid duplicate counts
Test Recorders automagically record subscription count
Nil checking for associated objects