Removes an unnecessary from Modifier\Storable
Tweaked Storable's functions about dirtiness

One function was removed, some others were renamed (of which one was
renamed to the previous name of another, but that shouldn't really matter)
Implemented a "zero protected" policy for Storable

The rationale is that this means there's less for collisions between
library defined functions and user defined inherited, since children are
simply not aware of their parents' privates.

This means some code duplication, but that only means a file size increase
for the generated files, and that amount is negligible anyway. The usual
nightmares with maintaining the code do not apply, since the code is
generated, meaning it's only in one place in the library code anyway
(it has just moved down a number of lines within the same file).
Updated Storable and Resolver interfaces

They now reflect what content the classes have.
Renamed AbstractResolver to BaseResolver
Creates StorableVisitor interface

It gets the functions on the subject that have been residing in Store so
far.

Now, this is the last bit of over-engineering to be removed. Next up,
we'll remove the fallout from the bit of desing we're correcting here and
then we can close the issue.
Removed fallout from the late acceptStore

Closes #23.