While adding the new 2013 subs to a new assembly I did notice that the 2012 version uses a different parameter list than the 2013 sub. It doesn't solve the problem but does suggest that bringing old assemblies forward to 2013 should not be recommended.
I have been struggling with the same problem for the past couple of weeks. The solution I found is to split my corridor into smaller regions where the rogue feature lines are happening.
I opened the "Creating Multiple Section Views.dwg" from the book Mastering civil3d 2012 using Civil 3D 2013 and the same thing happened, feature lines cross through ignoring multiple sections. I think it may be a graphics (visual) thing, The surface created from it seems normal. Also, changing the frequency will make it change or disappear.
If the corridor surface is built from links only then the crossing feature lines aren't a problem, but if they are used either as part of the surface definition or the boundary then it goes fubar.