Create means to eliminate overhead at the compiler or configuration level. Compiler would be better because it would have 0 overhead in the resulting app; whereas config would have to check if the area was desired.

The use case for me is that I have an app, 100% non-visual. It runs as a batch job. This app could/should be able to run faster if it didn't bother doing things that a non-visual app doesnt care about. ie - master/detail.

Most libraries I have seen have a configurable .INC which control what the behavior is at compile time. This would be nice to have it for certain areas

Lots of stuff that is under TOraSession configuration and TOraDataSet config (and presumably how they interact with any monitoring features) can be optimized via this type of approach. The code wouldnt even be compiled it .. and therefor, much faster in batch type of environments.

If this not achieveable, then a detailed best practices document for such environments / use cases.