Cannot archive-restore an archive-backup that was made from a symlinked DRUPAL_ROOT

Problem/Motivation

In our production setup, we point a "current_www"-symlink to the DRUPAL_ROOT folder. When doing an archive-backup, the "docroot" written to MANIFEST.ini will be the symlink, instead of the actual target (a directory with a timestamp name) of the symlink.
Trying to restore the archive in a different environment (local dev) with a different destination-parameter, we get this error:

Source directory /tmp/drush_tmp_somenumbers/current_www is not readable or does not exist.

This happens because drush always resolves the 'current_www' symlink to DRUPAL_ROOT for naming the Drupal directory contained by the archive, but when restoring, it infers the Drupal directory from the manifest.

Proposed resolution

The easiest solution here should be to wrap the docroot written to the manifest in a realpath() call, so the symlink gets resolved. This solves the problem in our case, but shouldn't introduce any incompatibilities either.

Remaining tasks

Another idea: instead of resolving the docroot, one might add the directory's name as an additional key to MANIFEST.ini and then use it for selecting the directory to copy from. This way, the original docroot could be used when extracting without setting --destination.