Allowed HydratingResultSet to accept a PrototypeFactoryInterface

[waddedMeat]

This change allows an instance of a PrototypeFactoryInterface to be used
instead of an object prototype. The factory will be passed the result
data and must return an object to be hydrated.

This would resolve Issue #18

[weierophinney]

Import ArrayObject, instead of using global qualifier. Same with ArrayIterator above.

[weierophinney]

I'm not convinced we need this; this sounds like a very application-specific use case, which would warrant a custom hydrator implementation.

As an example, you could overload DelegatingHydrator::hydrate() to introspect the $data argument to determine the object type to pass to its getHydrator() method. This seems like a cleaner solution than altering zend-db, as it separates the logic of object creation from the zend-db component — which was the original point of having the HydratingResultSet.