Basically anyone who isn't EastWest works fine with fast bounce. In fact, most programs will tell you it is the preferred method because it more properly might be called "offline bounce" meaning that the bouncing happens independent of the clock. Things process as fast as they can, but wait as long as they need. So if there is a dely fetching sample data, the DAW waits until it is complete. You can actually, in theory, have a "fast bounce" that takes longer than the song length if you loaded it so full of stuff that your computer couldn't process it in realtime. So you could have a project that was having crackles and dropouts in realtime, then you do an offline bounce, and everything sounds flawless because it can wait as long as it needs.
However, EW just can't handle this. I don't know why, but they just are married to the idea of realtime bounce and won't fix their software. It really isn't a bug, it isn't like it is something that just cropped up, it is a problem they've had since day one and just refuse to deal with.
I don't recommend using them, even with lots of RAM, because you can STILL have issues with fast bounce. They are much less likely, but in the event something happens, like some process on the PC happens to hit memory access hard at the wrong moment, you can get a glitch. Likewise why realtime bounce is not a good idea (aside from being slow) because if something happens to cause an interruption, you get a glitch.