I understand your frustration. Frustration is a big part of game development however, and you're going to have to learn to keep your cool, because it happens often. Encountering bugs in tools is something that even professional game developers have to deal with using pro middleware that costs thousands and thousands of dollars (I've heard them talk about it). Ashley is extremely responsive in fixing the bugs. Some of those pro companies making middleware I've heard talked about aren't, leaving the game developers with no recourse but to try to work around it somehow.
What if it is a bug in your events and not C2? Should Ashley spend all that time fixing the bugs in their users projects? Especially if that bug is complex, in a complex game. I had a weird bug that took me months to fix in my RPG. It seemed to make no sense, but I eventually figured out what it was doing. It's unreasonable to ask Ashley to dig through thousands of lines of code to find bugs that might not be bugs in construct.
It shouldn't take that long to strip it down to the bare essentials of what causes the bug, because you coded it and you know what does what. You can delete an entire half of the code in one shot and run it for example, if it's still there than you know what half of the code the bug is in. Considering the mountain of work that goes into game development, it's not that much work to do. And besides, think of all the time that they're saving you making C2 so you don't have to code your game from scratch yourself!