I gave a reply to Eric Handbury in this list (message #20663) about this problem and he replayed privately to me:
-----------

>Macro,
>
> Thanks for the e-mail. I did a quick check and it looks like your code
>stops the resource problem. I have been working on other things lately and I
>will get back to it in the next few days and really make sure the problem is
>solved. Thanks for your help.
>
> Eric.

Let's hope! If so, please share the changes back to Jason (and send a mention to the list), so all IBO comunity will benefit from this fix that surely will be included in the next subrelease.
regards
Marco Menardi
-----------
So or Eric or Jason forgot about that... Jason, could please check?


for your convenience, my suggestion was this (message #20663):
-----------------------
From: "Marco Menardi" <mmenaz@l...>
Date: Tue Sep 24, 2002 5:39 am
Subject: Re: Memproof errors (Repost)

As you can see in the "credit" section of the source, I've tried to reduce memory leaks of that component, that was preventing me of using my program in Win98. Since I moved to Win2000, I corrected the code when also in Win2000 I had some problem, but since I'm not a Win guru and, as far as I've read in Google, .Assign has changed from old delphi version to new one, there is a lot of confusion about it's usage.
Anyway, I've find that is good after and assign to use the following code:
Buttons[i].Glyph.Assign( My_Glyph );
Buttons[i].Glyph.Dormant;
Buttons[i].Glyph.FreeImage;

so could you try to add the Dormand and FreeImage line when apropriate inside the SysStateChanged procedure? I think that eliminate resource leaks is the better way to avoid "impossible" bugs later...
Let me (and the list) know
Thanks
Marco Menardi
------------------------

So hope this will be the right time to fix this definetly and, if you confirm that the patch works and has no collateral effects in Win2K, include it in IBO distribution.

regards
Marco Menardi