title: Durandal 2.0 routing parameterized routes (same route different parameter)
body: <p>I am probably missing something basic, but when building navigation I am attempting to define multiple parameterized routes in the shell.  The idea is that all of these routes will pass the user through to the same view/vm, but the parameter will determine content that is displayed after an ajax call).  The routing itself works well, but the title is always passed through from the first route in the list.  </p>
  
  <pre><code>activate: function () {
      router.makeRelative({moduleId: 'viewmodels'}).map([
          {
              route: 'grid/:page',
              title: 'Title 1',
              moduleId: 'grid',
              nav: 3,
              hash: '#grid/param1'
          },
          {
              route: 'grid/:page',
              title: 'Title 2',
              moduleId: 'grid',
              nav: 2,
              hash: '#grid/param2'
          },
          {
              route: 'grid/:page',
              title: 'Title 3',
              moduleId: 'grid',
              nav: 4,
              hash: '#grid/param3'
          },
          {
              route: 'grid/:page',
              title: 'Title 4',
              moduleId: 'grid',
              nav: 5,
              hash: '#grid/param4'
          }
      ]).buildNavigationModel();
  };
  </code></pre>
  
  <p>So, regardless of which of the generated links a user clicks on, the Title is always returned as 'Title 1'.  Nav order does not matter.  The first physical object in the list will supply the title for all links.  If I hard code the links into shell.html and use a splat in the router I do not have this problem, however, hard coding the links is not feasible nor desirable for the app.   </p>
  
  <p>So, the question is, what am I doing wrong?</p>