Are you suggesting that syntax errors create memory corruption?
Quoting: "even getting built-in library calls and macros right, on 1st attempt, becomes nearly effortless"...
Getting the syntax to parse != getting the correct syntax (meant for the job).
Even an off by one error in a library call can create memory corruption. Preprocessor macros? They can fuck everything if done wrongly.
Those are semantic errors, and a language aware editor will not fix them.
And yet, it's this "nearly" that creates all the huge C buffer overflow and memory corruption bugs...