Previous button trigger

I actually have a problem with the way Storyline handles navigation history. Two problems, in fact.

First, there is an asymmetry in Storyline's navigation that creates a big problem.

The idea that previous in Storyline works "similar to a browser" is true.  Unfortunately, next does not. A web browser does not have a concept of next until the user has used the back button or otherwise gone back in his/her navigation history.  The navigation the browser enables by next and back is constrained entirely to the sequence of pages/locations that the user has selected (not counting JavaScript, redirects, etc.).  In web browsing, there is typically not a concept of a next page unless you are in a context that introduces that idea, such as a product list, procedure (like checkout or registration), or series of pages in a multi-page article.  However, in Storyline, there usually is an identifiable next page (discounting last slide or branching), and that is the content that is intended by the author to be seen immediately following that of the current slide.  So, while Storyline's previous works precisely like a browser's back button, Storyline's next button works nothing like a browser's forward button.  By default, previous deals with history, but next deals with the "natural" ordering of slides.  And here is why it's a big problem...

Suppose I have slides A through E.  The user clicks next four times to get from A to E.  If I want the user to see slide C only once, I remove C from the content menu, use a project variable to record the visit to C, and override the next trigger on B and the previous trigger on D.  Now, here's what happens as I click previous multiple times from E: I see D, then B, then D, then B, then D, etc.  The looping arises as follows: D's previous is overridden to go to B, and B's default previous goes back in history to D.  It's an infinite loop, and not at all what the user desires/expects.  So, to maintain user expectations, if I override the previous trigger in one slide, I have to override previous triggers in ALL slides.

Second, the navigation history is recorded in the suspend data and thus grows with user navigation.

The record of navigation events allows the user to resume where he/she left off in the SCO and get the same behavior he/she would get in hitting previous, for example, before ending the preceding learning session.  That sounds nice, but there is a cost.  The suspend data (fairly limited in SCORM 1.2) grows.  I found that it grows quickly and linearly (each nav event adds several bytes to the suspend data length).  When I override all previous triggers (rationale explained above), even going "back" adds to the full nav history that is recorded and, as a consequence, increases the length of the suspend data.  The longer the user reviews the material, the greater the chance the suspend data will exceed limits and (as I've found anecdotally) we find some users are loosing their progress.

Can Storyline be made to save state minus navigation history (at least across sessions)?

Can Storyline be made to have symmetrical navigation?  That is, can Storyline adopt a browser style OR (my desire) handle its default previous trigger the same as its default next trigger?  I don't think the (semi-web browser) navigation history is valuable.

Thanks,

-Andre