Here are a few lines of TypoScript code that really took me a long time to get to.

In TYPO3 4.x, I would fetch an image which is inserted on a certain page as a normal content element (CE) and use it for example as an site wide header image.
In this example, the image in question is located in the backend column 'left' (id 1) on the root page of the site, the PID of that page is stored in a TS-variable {$home_dir}, since I change it further down the page tree via TS-constants.

TYPO3 4.x

temp.headerimg < styles.content.getLeft
temp.headerimg {
  select {
    pidInList = {$home_dir}
    max = 1
  }
  renderObj = IMAGE
  renderObj {
    file.import.field = image
    file.import = uploads/pics/ 
    stdWrap.typolink.parameter = {$home_dir}
  }
}

With TYPO3 6.2, this won't work, since the image/file handling has fundamentally changed with the introduction of the FAL (file abstraction layer). I had lots of funny effects before I arrived at this working solution:

TYPO3 6.2

temp.headerimg < styles.content.getLeft
temp.headerimg {
  select {
    pidInList = {$home_dir}
    max = 1
  }
  renderObj = FILES
  renderObj {
    references {
      table = tt_content
      fieldName = image
      uid.data = uid
    }
    renderObj = IMAGE
    renderObj {
      file.import.data = file:current:originalUid // file:current:uid
      stdWrap.typolink.parameter = {$home_dir}
    }
  }
}

The above works and enables you to turn off the fallback "contentAdapter" in the Install Tool, which, if enabled, makes sure that your legacy 4.x TypoScript will work, but slows down the FE rendering quite a bit, and TYPO3 will make sure to remind you of this fact if you have a look at the "reports" tool in the back end.

Since I didn't find this use case (content image, not page:media image) and the according TypoScript anywhere, maybe this is of some help to others.