v5.0.0.20: Fix to core engine memory issues seen on a small minority of systems

One of the optimizations I employ is reusing memory instead of having to free and reallocate it. Yes, it does make things a bit more complicated, but it improves efficiency considerably. Sadly, while I reviewing the code I saw a logic error that needed repairing. I have no idea if it ever manifested in the real world, I've not seen it. It would have manifested most likely as a crash.

However, I did fix something that I know did manifest in an XP test bed I have with a unique software environment that includes NIS 2011: a very small memory leak in the core engine. I do not know how many systems were affected, I certainly have not seen this on any other test beds. Also, it is a very small and slow leak that would take a good amount of time to build up (and be continually paged out in the meantime). So, it is unlikely anyone who was affected actually noticed. Regardless, I repaired it and am issuing this update.

Thus, we have v5.0.0.20:

• [.20]Fix.Core: Fixed a logic error in memory reuse optimization (unknown if manifested in real world)
• [.20]Fix.Core: Fixed a small memory leak seen in exhaustive testing under XP /w NIS 2011 present (special handling involved with NIS2011)
• [.20]Change.GUI: Updated Serbian Latin
• [.20]Change.GUI: Updated Finnish

Please keep in mind that version 5 was a large leap, and I certainly do wish I had polished it more prior to the first final version. However, we are where we are, and I can say that it is now where it should have been to start with. Yes, I am embarrassed with the admission that I discovered more bugs. At least I discovered these before they were even reported, for what it is worth ;).

The polishing continues... I already have another minor update to improve a few cosmetic non-critical issues in the GUI coming down the pipeline. Of course, this goes without saying, I always have a new build coming down the pipeline.