I see
generally speaking can there be put a limit (number of database record, number and/or type of operations on them, other...) above which the better performance trade off is or can be actually worth the risk for fatal crashes?
I'm aiming at the awareness that for my actual uses it will never be
I'll have to defer to someone more experienced than I to answer that, as I've been **perfectly happy with the performance of using Transactions + using block, and have never even tried - figured I'd leave that for the to-do list when I decide to step up into ObjectARX (C++ for AutoCAD).
** What I've not been happy with is Civil 3D-specific Objects not having sufficient .NET API exposure, to allow me to obtain the information I need without exploding in memory (not actually exploding the source Object), which is incredibly inefficient, just so to cull the information I'm after; example: Alignment Station Offset Labels. Grrr