Forward declare PhaseUsage as struct, not class.
Merge pull request #83 from atgeirr/fix-warning-struct-class

Forward declare PhaseUsage as struct, not class.
Remove rs_or_sg_eq from the residual.

This has not been used since the introduction of live gas changed
the treatment of rs (and rv) values to make a more compact system.
Merge pull request #84 from atgeirr/remove-unused-residual-part

Remove rs_or_sg_eq from the residual.
Merge remote-tracking branch 'upstream/master' into opm-parser-integrate
Trying to get the test back running, by looking at the sim_fib_ad main method. Please advice if the string casting on line 335 is bad stuff, not my strongest side
Changed back arguments of runWithXParser to use ParameterGroup
Removed comment
Const-ref of parameter to the runWithXParser() functions
Reverting some const_casting, that was introduced with no real reason
make the deck from opm-parser available to the black-oil PVT property classes
use the new parser to read the PVT and grid data from the deck

the old code has not yet been removed, but in the long term, this is
probably the way to go.
really use the new parser

in the previous commit this was #if 0'ed...
switch to the new parser's table utility classes
sim_fibo_ad: completely replace the old eclipse parser by the new one

this required to abandon the "Epoch" stuff which the new parser does
not have (as well as the ECLIPSE file format knows nothing about
epochs). Handling well controls properly thus has to wait until Joakim
and Kristian finish refurbishing the WellsManager, so as a stop-gap
measure, only the first "epoch" is run.
BlackoilPropsAdFromDeck: Add support for PVTO
sim_fibo_ad: add macro to easily switch between the old and the new parser
adapt to the changes in the APIs of the parser-integrate branch in opm-core

Since the SimulationTimer, EclipseWriter and WellsManager stuff has
not (yet?) been merged, the old parser is required to be around. Use
my parser-integrate-hacks_for_norne branches to test your stuff on the
Norne deck...
re-add the epoch stuff

this is required until the new time step handling code lands...
first write out the result of a time step, then increment the timer

if done the other way round we would make an assertation in TimeMap
false and also the values returned by SimulationTimer would be for the
next time step and not the current one...