[edit]Maybe, it has changed in the meanwhile, but this doesn't help, when the user knows the model's filename, because then the engine prefers the model outside of the resource against that in the resource.[/edit]

I didn't know that...

[edit]What we can implement, however, is an option to lock a resource so that its content can't be replaced.[/edit]

This would be indeed useful.