Swapped expected/actual exception message

The first argument to `Assert.AreEqual` is the expected value, and the
second is the actual value. The values being passed in
`AssertExceptionMessage` were backwards, which can be confusing when
evaluating test failures.
Merge pull request #6 from amazingant/master

Swapped expected/actual exception message