Pass/failure behaviour of toBeIn is correct; user messages needs to be handled
User messages handled in toBeIn
Changed numbers being tested to two equivalence classes. This should make evolving the tests
to a BDD style setup of one testcase per fixture easier
toContain pass/fail logic implemented
Tests continue running when on test has failed
User messages prepended to messages for toContain()
Merge pull request #17 from iain-peddie/containers

Containers