Calling delete on a NULL pointer does nothing. Checking for non-NULL just
clutters the code.

Still, I wonder if this code has some issues with heap corruption and/or
leaks. The pImagesLst->GetEntryData() calls just return a copy of the OUString
pointers stored in some kind of list, right? So is it correct to call delete
on the copy, but keep the pointer in the list intact, which thus then will be
pointing to freed memory, won't it? Or will the code automatically work in
such a way that all pointers in the list will be handled exactly once (and
deleted)?

Perhaps running this under valgrind would be a good idea.

Change-Id: Ibf401cc44caaeea6bb46f38cd9851ac14b2d2545