The really irritating thing about this is that there's no way to tie automation data to midi/audio clips in a reliable way. Start moving stuff around and it all falls apart. When I'm using Cubase I just use midi ccs instead of automation, since they at least can be.
I have no problem with automation linking to audio parts...it moves with the part perfectly.
But, yes, it is a pretty big oversight to not allow automation to move with midi parts, I fully agree.
I wonder how much automation is a problem of plugin developers though - I don't know the full VST2 spec list, but isn't midi control part of it? If all developers simply coded plugins that have midi control, it wouldn't be a problem. Some plugins I use (even some quite old ones) allow midi cc control and it makes them so easy to use. Some on the other hand have none...but I'm not sure that's Steinberg's problem. If only all devs made plugins similar to impOSCar - an edit page for the whole plugin where you simply type in whichever midi cc you want to control whichever knob. It's elegant, I would imagine simple to code, and it makes the synth so incredibly useable in any setup. If synth/FX developers all did that, we wouldn't be moaning about automation within SX. And to me, that makes it a developer shortcoming, not Steinberg.