dealt with the known issue with a custom matcher
that's effectively eq() except that it will test
expected == actual. As a result, the arg_that
matcher will be the one doing the == comparison in
each case.

==/eq matchers will work for built-in types and
with simple collections, but will not invoke the
arg_that block in most real-world cases.
docs
0.1.0