Updated 2 test cases to outline two major issues with the new hydration (at least i think that it has to do with the problems):
1) When the result set is in a custom order, components may be doubled (this already occured half a year ago though the symptoms were different (items were assigned to the wrong collection).
2) Accessing related components that are already loaded (but empty) results in lots of extra queries. The only way to get around that is do wrap an isset() check around nearly all places before accessing a relation. This was not the case in earlier revisions though at that time an isset() was sometimes needed, too to prevent extra queries. But now it seems to be necessary everywhere.

--no commit message

--no commit message

--no commit message

fixing the XSL sheets to use the programlisting XSL files in the svn repos. This really is quite a nasty way of doing it - absolute paths should not be in SVN, not sure how to fix it yet

Sorry for the trigger happy commits, but with each one I'm
actaully trying to fix some post-commit script magic :)

--no commit message

--no commit message

--no commit message

--no commit message

--no commit message

--no commit message

docbook output is now generated into a singlefile called "doctrine.html", and a whole set of files in the "html" folder.