I have no idea, Michael, other than not enough people complain about what isn't being fixed. When I submit a defect in the API I must provide them with a business case as to WHY I need it., which includes:
Impact on your application and/or your development.
The number of users affected.
The potential revenue impact to you.
The potential revenue impact to Autodesk.
Realistic timescale over which a fix would help you.
In the case of a request for a new feature or a feature enhancement, please also provide detailed Use Cases for the workflows that this change would address.
So perhaps if more people were very specific about what needs to be fixed, why it needs to be, and the $$ it's costing them by not being fixed, then more might get accomplished? But I see more "It's broke, fix it, its still broke, why haven't you fixed it" comments over yonder than anything else.