XML Compare shows wrong file content, huge memory footprint

I'm enjoying to use net.sf.colorer_0.6.0 on eclipse 3.0
on Win2000, however... ;-)

Probably these problems are all related to another,
that's why I file them together as one report.

Problems are:
- When showing xml files in diff view, clicking the
tree view on top of the compare editor (labelled "XML
Compare (Ordered)") shows wrong file content
- Tree sometimes contains structural differences even
if there aren't any or doesn't navigate to real
differences but shows matching content
- memory consumption during diff of big xml files is
extremely huge.

Steps to reproduce:
The attached zip file contains three pairs of xml files:
* tiny-xml1.xml
* tiny-xml2.xml
* medium-xml1.xml
* medium-xml2.xml
* huge-xml1.xml
* huge-xml2.xml
Unpack them into an eclipse project. (note: 6KB Zipfile
contain 632KB well compressed XML)

With the "tiny files":
1. Mark both files and choose "Compare With -> Each
Other" from context menu
2. Note that the differences are correctly shown (one
file contains a tag more than the other)
3. Double click on "eclipseXmlTest[1]" in the "XML
Compare" tree in the upper part of the compare editor
4. Note that the closing tag "</eclipseXmlTest>" has
disappeared.
We also experienced this with different amounts of text
from the last line (the closing tag) disappearing, not
necessarily the whole line.

With the "medium files":
1. Mark both files and choose "Compare With -> Each
Other" from context menu
2. Note that the differences are correctly shown (one
xml-comment differs)
3. open all levels in the "XML Compare" tree in the
upper part of the compare editor by clicking the "+"
4. Note that the Tree does not correspond with the
document - The difference seems to be in

eclipseXmlTest[1]-someRandomTag[20]-andEvenAnother[1]-
body(1) and body(2) (but it is in a comment).

With the "huge files":
1. Open Task Manager, note memory consumption. (restart
eclipse to be clean)
2. Mark both files and choose "Compare With -> Each
Other" from context menu
3. Note that memory footprint jumps up by more than
2000 MB for comparing two files of 290 KB each (I've
even had eclipse crashing on several occasions)
4. If you like: You can reproduce the same errors as
above.