Answer
Rather than the DBImage() function, concatenating the relevant data field (like the user who printed or authorized the document) together with the image file extension inside the Signature() function has worked for dynamically resolving the correct signature image at print time — for example, building the image name from a processing/authorization attribute on the record — as long as a matching signature image is loaded into the report's image repository for every value that can appear.