I think most of your class size bloat comes from the different API classes you make use of all of which add to the class's symbol table size.
I'll take a look and see if there's any way I can trim this down.
i would suggest try using only one array and use different Index offsets for logically different instead of many different arrays each representing a different logical component.
I was going to have a single array with different indices being the different variables I needed (for the singleton variables) but it seemed that that would actually add to the size. There's only a couple of other arrays that I could do this for, but I'll keep this in mind.
Try reducing the number of local variables used. If you can, reuse a local variable for different logical purposes.
I've been trying to reuse wherever possible, but I'll look harder for more opportunities.
try using the ? opertor when conditionally assigning values...
Is this true? I thought someone, way back when, said that this way actually took more bytes...
if possible convert all for loops to loop backward. The comaprision to 0 test will therefore occur often and be more easily compressable.
Thanks for taking a look!