While Writer is able to load linkes graphics asynchronously and in a separate
thread, all applications using the SdrGrafObj block the application in a twofold
way: first in SvxGraphicObject::setPropertyValueImpl where a superfluous filter
detection is carried out and at the time where the graphic finally it "swapped
in". By throwing out the filter detection of the importer (and doing it later on
demand, in case it's needed at all) and swapping in the graphic in the same
asynchronous way as in Writer, the performance of documents containing linked
graphics, especially remotes pictures, will be improved considerably.

As Writer is going to throw out its own graphic objects, not fixing this problem
will be a performance regression for Writer.