Implement ArrayAccess in DomainObject
Use __set and __get instead of internal methods
Close method for sequence pool connections
Merge pull request #71 from dhotson/close-sequence-pool-connection

Close method for sequence pool connections
Updated roadmap to reflect present plans
Update phpunit dependency
Remove stray apostrop'he
Indentation
Use phpdoc-style @throws declaration
Update doc comment to reflect reality
Merge pull request #74 from lox/misc-tweaks

Misc tweaks - whitespace and docs
Merge branch 'array-access-support' of git://github.com/arthens/pheasant into array-access-support

* 'array-access-support' of git://github.com/arthens/pheasant:
  Use __set and __get instead of internal methods
  Implement ArrayAccess in DomainObject

Conflicts:
	tests/Pheasant/Tests/DomainObjectTest.php
Fix bug #60, changes are only tracked when they are actually changes
Collapse RelationshipType into Relationship
Merge pull request #75 from lox/refactor-relationships

Collapse RelationshipType into Relationship
Adding onHydrate event and onEvent to Domain Objects
Adding another test for finding
Default string coercion strategy for domain objects

Produces a string containing the table name and a stringified version
of the object identity. E.g. per the test case, an `Animal` with
`id=1` is stringified to `Animal[id=1]`.
Follow code style
Throw more specific exception when 0 rows found

Applications will want to handle a 0-row result differently from an
n-row result from a call to `Collection::one()`.

E.g. a 0-row result might be rethrown as an HTTP 404 error, while an
n-row result might indicate a data integrity error (i.e. an HTTP
500 error).

Semantically I don't think `NotFoundException` extends
`ConstraintException`, but it's implemented this way for backwards
compatibility.