Why mono-1.9 is required?

SUGGESTED MONO VERSION is 1.9. Memory handling was one of the things I wanted
to fix for this release. But Mono 1.9 solves everything. From stopwatch example allocating
100kb/23sec, Mono 1.9 holds memory allocation steady as a rock. Memory handling is
one of the things now tagged with WONTFIX. Can't fix since it ain't broken. Even with crazy
pointer Adaptors swapping in stopwatch memory sticks at almost the same place.

mono-1.2.6 (result of running stopwatch sample for 7 hours and 20 minutes)
(after few seconds) - 8.7MB allocated
126soon
(after 7 hours 20 minutes) - 115.6MB allocated (being just left alone)
126atend
stopwatch in this case was left alone as possible without any item selection for result to be as slim
as possible

mono-1.9 (result of running stopwatch sample for 7 hours 30 minutes)
(after few seconds) - 10.9MB allocated *** machine is 64-bit so starting consumption being bigger is normal
19atstart
(after 7 hours 32 minutes) - 12.9MB allocated (with all my troubles to increase it)
19atend

after holding result steady at 10.3MB for hour or two, I started stressing run as much as possible
with changing selected item, but result never got past 13.2MB.

Just to note few things:
item selection in this case is a lot more stressing than just updating treeview item. Updating
treeview goes trough cached mapped properties which means not even one simple property
discovery is happening at that point (treeview has its default mapped type), while Adaptors
on the other hand often have no clue what they are dealing with. And if this is not enough,
there is also complete target messaging which happens on every target change.

Growth rate with 1.2.6 for this kind of stressing was 130kb/sec