Everybody already forgets the time when associating safe marks were very-very slow even when there were not safe marks at all. Moreover, due to absence of proofs to be analyzed somehow, safe marks are still exotic, that can be useful in quite artificial cases, namely for testing and validation verification jobs that are obviously are out of the normal user workflow. In those days we had to disable safe marks either globally (enabled by default) or per individual verification jobs (also enabled by default). The first option is harmful, so, we will get rid of it soon (#9088). (#9008). The second one needs some investigation. If highly loaded production servers will not suffer much from enabling safe marks for all verification jobs, we will be able to get rid of it completely.