You need to consider not just the memory access itself, but the consequences of preventing it. With a compile time check, there's a development cost but absolu

You need to consider not just the memory access itself, but the consequences of preventing it. With a compile time check, there's a development cost but absolutely no runtime consequence. With a dynamic check, sure the memory access is detected and blocked. But if you stop there the application crashes, which may be completely unacceptable. In an embedded system such a crash may be as bad as the incorrect access itself. More generally, the issue is not so much the incorrect access than its possible adverse consequences. With a compile time check, there are no runtime consequences. With a runtime check, there are still runtime consequences: either the impact of an application crash, or the extra error handling code and behavior to deal with the detected wrong access and mitigate it at runtime. Whether such consequences are acceptable or not depends on the context, but it's there and do make a difference with a compile time or static analysis check.