Broken node rendering

The [node-content] token provided by the Content Notifications module seems to be interfering with the rendering of nodes "live" on site.

A theme with a node.tpl.php that renders node content "field by field" and includes a call to print $node->content['body']['#value'] would normally output only the HTML for the body field. However, with the Content Notifications module enabled, this call produces the same output as a call to print $content (fully rendered node content including all CCK fields as per display settings).

When combined with various calls to print CCK fields what results is a big mess with many fields outputted twice.

Commenting out the lines in notifications_content.module that define the [node-content] token fixes the problem - as per the sample below:

notifications_content.module @ line 907 ...

function notifications_content_token_list($type = 'all') {
  $tokens = array();
  if ($type == 'node' || $type == 'all') {
    $tokens['node']['node-teaser']    = t('The node teaser.');
    $tokens['node']['node-body']    = t('The node body.');
    //$tokens['node']['node-content']    = t('The fully rendered node content.');
    ... etc

notifications_content.module @ line 927 ...

function notifications_content_token_values($type, $object = NULL, $options = array()) {
  switch ($type) {
    case 'node':
      if ($node = $object) {
        $values['node-teaser'] = !empty($node->teaser) ? check_markup($node->teaser, $node->format, FALSE) : '';
        $values['node-body'] = !empty($node->body) ? check_markup($node->body, $node->format, FALSE) : '';
        $values['node-url'] = url('node/'. $node->nid, array('absolute' => TRUE));
        $values['node-teaser-raw'] = !empty($node->teaser) ? $node->teaser : '';
        $values['node-body-raw'] = !empty($node->body) ? $node->body : '';
        // Fully rendered node content
        //$node = node_build_content($node);
        //$values['node-content'] = drupal_render($node->content);
        ... etc

I'm not a drupal guru, but I suspect that the call to node_build_content is somehow replacing the "cached" copy of the node used for the lifetime of the page request, and this "mangled" node is being re-used by the page output?